Dashboard Editor

ABSTRACT

A user interface programmed to create a digital dashboard includes a dashboard workspace including one or more zones, and a dashboard elements area including a plurality of dashboard elements. A dashboard element of the dashboard elements is dragged and dropped onto one of the zones to add the dashboard element to the digital dashboard.

BACKGROUND

A digital dashboard, sometimes referred to as an enterprise dashboard oran executive dashboard, is a tool used by a business to gauge the healthof the business. Typically, the digital dashboard provides a visuallayout of key performance metrics for the business pulled from a varietyof data sources.

A digital dashboard will typically show one or more Key PerformanceIndicators, also known as KPIs or Key Success Indicators (KSI). KPIshelp an organization define and measure progress toward organizationalgoals. Once an organization has analyzed its mission, identified all itsstakeholders, and defined its goals, it needs a way to measure progresstoward those goals. KPIs are used to provide those measurements.

KPIs can be organized on the dashboard into one or more scorecards.Scorecards are used to provide detailed and summary analysis of KPIs andaggregated KPIs such as KPI groups, objectives, and the like. Businesslogic applications that generate, author, and analyze scorecards aretypically enterprise applications with multiple users (subscribers),designers, and administrators.

SUMMARY

In one aspect, a user interface programmed to create a digital dashboardincludes a dashboard workspace including one or more zones, and adashboard elements area including a plurality of dashboard elements. Adashboard element of the dashboard elements is dragged and dropped ontoone of the zones to add the dashboard element to the digital dashboard.

In another aspect, a method for creating a digital dashboard includes:creating one or more zones in a dashboard module; dragging and droppinga scorecard or report onto a zone; dragging and dropping a filter ontothe zone; and linking the filter to the scorecard or report.

In yet another aspect, a method for creating a filter that is programmedto modify one or more scorecards or reports in a digital dashboardincludes: allowing for selection of a filter template from a pluralityof filter templates, the template defining a type of the filter;allowing for selection of a data source for the filter; allowing forselection of filter parameters from the data source; allowing forselection of a display method for the filter; and compiling the filterfrom the filter template, the filter parameters, and the display method.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

DESCRIPTION OF THE DRAWINGS

The accompanying drawings incorporated in and forming a part of thespecification illustrate several aspects of the present disclosure, andtogether with the description serve to explain the principles of thedisclosure. In the drawings:

FIG. 1 shows an example system including a client, a dashboard server,and a data source.

FIG. 2 shows an example template interface for selecting a template fora dashboard.

FIG. 3 shows an example name interface for naming a dashboard.

FIG. 4 shows an example dashboard editor for creating a dashboard.

FIG. 5 shows the dashboard editor of FIG. 4 with a KPI dragged anddropped onto a zone of a dashboard workspace.

FIG. 6 shows a portion of the dashboard editor of FIG. 4 including anadd to zone control.

FIG. 7 shows a portion of the dashboard editor of FIG. 4 includingseveral zones of a dashboard workspace.

FIG. 8 shows an example edit item interface for editing properties of azone of a dashboard.

FIG. 9 shows another view of the edit item interface of FIG. 8.

FIG. 10 shows the dashboard editor of FIG. 4 including a filterworkspace.

FIG. 11 shows an example filter template interface of a filter creationwizard.

FIG. 12 shows an example name interface of a filter creation wizard.

FIG. 13 shows an example data source interface of a filter creationwizard.

FIG. 14 shows an example select members interface of a filter creationwizard.

FIG. 15 shows an example dimensions interface of a filter creationwizard.

FIG. 16 shows an example selecting member interface of a filter creationwizard.

FIG. 17 shows the select member interface of FIG. 14 with examplecontent displayed.

FIG. 18 shows an example display method interface of a filter creationwizard.

FIG. 19 shows an example confirmation interface of a filter creationwizard.

FIG. 20 shows an example dashboard editor including a filter in a zoneof a dashboard workspace.

FIG. 21 shows another example dashboard editor including a filter thatis dragged onto a scorecard in a zone of a dashboard workspace.

FIG. 22 shows another example dashboard editor with a filter added to azone of a dashboard workspace.

FIG. 23 shows the dashboard editor of FIG. 22 with the filter draggedonto a scorecard in another zone of the dashboard workspace.

FIG. 24 shows an example edit filter link interface with a link optionstab selected.

FIG. 25 shows the edit filter link interface of FIG. 24 with a linkitems tab selected.

FIG. 26 shows the dashboard editor of FIG. 22 with the filter added tothe scorecard.

FIG. 27 shows a portion of an example dashboard editor with a menu forediting a zone of a workspace.

FIG. 28 shows an example zone settings interface with a general tabselected.

FIG. 29 shows an example zone settings interface with a size tabselected.

FIG. 30 shows an example zone settings interface with an orientation tabselected.

FIG. 31 shows another example dashboard editor with a zone in aworkspace expanded.

FIG. 32 shows an example dashboard that is published to a server.

FIG. 33 shows an example method for creating a dashboard.

FIG. 34 shows an example method for creating a filter.

DETAILED DESCRIPTION

The present application is directed to systems and methods for creatingand editing digital dashboards.

FIG. 1 shows a basic system 100 for dashboard implementation. The system100 includes a dashboard server 102, a client database 104, and a client106. While the three elements of system 100 are shown communicatingdirectly with each other, the dashboard server 102 can interact with thedatabase 104 and the client 106 over a network (not shown) forperforming rendering dashboards.

The network can be a secure network such as an enterprise network, or anunsecured network such as a wireless open network. Such a network isintended to provide communication between the nodes described above. Byway of example, the network can include wired media such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media.

The system 100 can also include any topology of servers, clients,Internet service providers, and communication media. Also, the system100 can have a static or dynamic topology. A business logic applicationcan be run centrally on the server 102 or in a distributed manner overseveral servers and/or client devices. The server 102 can include anumber of information systems, such as performance measures, businessscorecards, and exception reporting. A number of organization-specificapplications including, but not limited to, financial reporting,analysis, booking, marketing analysis, customer service, andmanufacturing planning applications can also be configured, deployed,and shared in the system 100.

In example embodiments, one or more dashboards including performancemeasures, business scorecards, and exception reporting are published tothe server 102 and are accessible to the client 106. In one embodiment,the server 102 is a MICROSOFT® Office PERFORMANCEPOINT™ Server 1007developed by Microsoft Corporation of Redmond, Wash. Otherconfigurations are possible.

The client database 104 is an example of a number of data sources thatcan provide input to the server 102. Additional data sources can includeSQL servers, databases, non multi-dimensional data sources such as textfiles or EXCEL sheets, multi-dimensional data source such as data cubes,and the like.

In example embodiments, the server 102 and the client 106 are computersystems. For example, the client 106 can be a personal computing device,such as a desktop or laptop computer, a personal data assistant, or acellular telephone. The client 106 can include input/output devices, acentral processing unit (“CPU”), a data storage device, and a networkdevice. Typical input/output devices include keyboards, mice, displays,microphones, speakers, disk drives, CD-ROM drives, and flash drives.Computer readable media, such as the data storage device, provide fordata retention. By way of example, computer readable media can includecomputer storage media and communication media. Computer storage mediaincludes volatile and nonvolatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer readable instructions, data structures, program modules orother data. Communication media typically embodies computer readableinstructions, data structures, program modules or other data in amodulated data signal such as a carrier wave or other transportmechanism and includes any information delivery media. The term“modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. Among the plurality of information stored on the datastorage device is a client operating system (“OS”) and clientapplications. The client OS is a program that manages the hardware andsoftware resources of the client system. The client applications utilizethe resources of the client 106 to directly perform tasks specified bythe user. The network device enables the client 106 to send and receivedata to/from the server 102. Other configurations for the client 106 arepossible.

In a typical application, users can interact with the server 102 runningthe business logic application from the client 106 and provideinformation as to what kind of scorecard calculation, on which data, andwhat type of reporting are desired. Based on the provided information,the server 102 can determine a hierarchy of a scorecard and retrievedata associated with the scorecard metrics from the client database 104.The server 102 can then perform the scorecard calculation and providethe digital dashboard with the desired information.

The dashboards and other metrics that reside on the server 102 and thatare presented to the client 106 can be created using the systems andmethods described below. For example, in one embodiment, a dashboard iscreated using a dashboard editor that allows business metrics, such asKPIs, to be dragged and dropped onto zones defined by the dashboard.

Examples of editors used to create dashboards are described below.

Referring now to FIG. 2, an example dashboard template interface 200 forselecting a template for the dashboard is shown. The template interface200 includes a template area 210 that lists a plurality of templates forthe dashboard. The templates provide a pre-defined layout for adashboard. For example, templates including one zone, multiple columnsor rows, and split columns can be selected from the template area 210.In this example, the template 220 for a dashboard containing a headerand two columns is highlighted. The user selects an OK button 230 tocontinue.

Referring now to FIG. 3, a name interface 300 is shown. The nameinterface 300 includes a text box 310 that allows the user to enter aname for the dashboard. A text box 320 allows the user to select afolder to store the dashboard. Alternatively, the user can click on aselect display folder button 330 to browse available folders for storageof the dashboard. The user can also allow authenticated users to viewthe dashboard by clicking checkbox 340. The user then clicks a nextbutton 350 to begin editing the dashboard.

FIG. 4 shows an example dashboard editor 400. The dashboard editor 400contains an example ribbon 410 with various control elements. Thedashboard also includes a workspace browser 420 for identifying wherethe dashboard and other metrics such as KPIs are stored, a dashboardworkspace 430 containing zones in which dashboard elements can bedropped, and an items area 440 containing available scorecards, reports,and filters that can be dropped into the zones in the dashboardworkspace 430.

In example embodiments, the scorecards listed in the items area 440 arecreated using a scorecard editor such as that disclosed in U.S. patentapplication Ser. No. ______, Attorney Docket Number 14917.0763U501,filed on even date herewith and entitled “Scorecard Interface Editor.”Other configurations and sources for the scorecards and other metricslisted in the items area 440 can be used.

The ribbon 410 includes control elements that allow the user to makestyle and format changes to the dashboard, update the data in thedashboard, and for publishing the dashboard to a server. For example,when a dashboard is complete, the user can select a publish icon fromthe ribbon 410 to publish the dashboard to a server, such as server 102.

For the example shown in FIG. 4, the dashboard workspace 430 includes aheader 460 and two zones 470, 480 created from the template selected forthe dashboard. The header 460 is at the top of dashboard workspace 430.The dashboard workspace 430 also includes three tabs 450 at the top (theedit tab is currently highlighted). Each tab presents a differentdashboard workspace view, as described below. In the example shown, theeditor view is selected for the workspace 430.

Referring now to FIG. 5, the dashboard can include multiple pages. Atoolbar 510 allows pages to be added, deleted or moved. Pages provideflexibility to the user in presenting the dashboard. For example, onepage can show an overview of key performance indicators. Another pagecan provide a detailed view.

In operation, an available item, such as a scorecard, report or filtercan be dragged and dropped from the items area 440 into a zone in theworkspace 430. For example, a fixed value scorecard 520 is shown beingdragged from the items area 440 onto the top zone 470 in the dashboardworkspace 430. When the fixed value scorecard 520 is dragged, an outline550 of the top zone 470 is highlighted (e.g., in a blue color) toprovide an indication to the user that the scorecard 520 can be droppedin the top zone 470. A zone can hold multiple scorecards, reports orfilters.

The dashboard editor 400 also includes an add to zone control 560. Theadd to zone control 560, shown separately in FIG. 6, allows the user tochoose an item in the items area 440 and then select a zone into whichthe item is added. For example, once an item is highlighted in the itemsarea 440, the add to zone control includes dropdown list button 610which displays the available zones in the workspace 430 (e.g., top rowand bottom row). The user selects the desired zone and then clicks anadd button 630 to add the selected item to the selected zone in thedashboard workspace 430.

Referring now to FIG. 7, the zones of an example workspace 700 are shownin more detail. A top row zone 705 includes a logical representation ofa scorecard 720 that has been added to the zone 705. The examplescorecard 720 includes a grab bar 710 for moving the scorecard withinthe zone, a title area 720, a drop zone area 730 in which filters areplaced, and a pull-down menu 740. The example pull-down menu 740contains options 750 for editing an item and 760 for creating a link.When option 740 for editing a link is selected, an example edit itemscreen 800 shown in FIGS. 8 and 9 is displayed.

In FIG. 8, the edit item interface 800 includes a general tab 810 and asize tab 820. The general tab 810 is highlighted, showing a displayposition text box 830 and cache option text box 840. The displayposition text box 830 allows the user to position the item in the zone.For example, if “1” is selected, this item is first in the zone. Thecache option text box 840 provides options as to how the item should becached or whether the item should be cached. When an OK button 850 isclicked, the changes are applied to the item, for example to thescorecard or the report.

FIG. 9 shows the edit item screen 800 presented to the user when thesize tab 910 is selected. The size tab 910 allows the user to adjust thewidth 920 and the height 930 of the item in the zone. The width andheight can be automatically adjusted to fit the zone or it can be userselectable, either by specifying a percent width and height for the itemin the zone or by specifying the exact pixel size for the width andheight. The changes are applied when an OK button 940 is selected.

FIG. 10 shows the dashboard editor 400 with the filter tab 1010 selectedto access a filter workspace 1005. The filter tab 1010 includes a filtermodule 1020, a linked items module 1030, and a details module 1080. Thefilter module 1020 provides a list of available filters. The linkeditems module 1030 provides a list of the items, such as scorecards andreports, to which the filters are applied. The details module 1080provides the details of related information associated with the filter,such as related KPIs, related scorecards, related reports, related datasources and related indicators.

The example filter module 1020 includes a new filter button 1040, adelete filter button 1050, and a filter list area 1060. The filter listarea 1070 provides a list of available filters. Similarly, the examplelinked items module 1030 contains an overview of the linked items area1070 which provides a list of scorecards and reports to which filtersare applied.

A filter wizard is provided to guide the user through the filtercreation. To create a new filter, the user clicks the new filter button1040. This brings up example new filter template 1100 shown in FIG. 11.A menu 1210 lists the various steps of the wizard and generally orientsthe user as to which step in the wizard the user is currently on.

The user can create a filter from a plurality of templates, includingMDX query, member selection, named sets, tabular values and timedintelligence templates. MDX query enables manual input of MDX to filterthe scorecard or report objects. Member selection allows the user toselect specific members from the data sources. Named sets creates afilter based on a named set. Tabular values creates a filter list fromtabular values. Time intelligence uses time intelligence members tocreate a filter. Time intelligence can also be used with formulas on thefilter links. For the example shown, the member selection template 1110is highlighted. The user selects an OK button 1120 to continue.

An example name interface 1200 is shown in FIG. 12 is provided. The userenters a name for the filter in text box 1210 and clicks a next button1220 to continue.

A data source selection interface 1300 is shown in FIG. 13. In theexample, only one data source for the filter is listed, the AnalysisServices data source 1310. In other examples, multiple data sources thatare associated with the selected filter can be shown. The user selects adata source by highlighting it and clicking a next button 1320 tocontinue.

This brings up a members interface 1400 for adding dimensions andmembers to the filter. To add dimensions to the filter, a selectdimensions button 1410 is clicked.

An example interface 1500 for adding dimensions to the filter is shownin FIG. 15. Example dimensions that can be added include account number,customer city and address, customer occupation and customer maritalstatus.

Referring now to FIG. 16, filter members are added by clicking theselect members button 1410 to access the select members interface 1600.The user can select a member for the filter from a list of availablemembers. In the example shown, the member 1610 for fiscal quarter 2 isselected. By right clicking on the selection, the user is present withexample options 1620 which allows the user to identify propertiesassociated with the selected member, as well as define a default member.

Referring now to FIG. 17, the members interface 1400 is shown with thedimensions and members that are selected.

Next, the user selects a display method for the filter in an exampleinterface 1800. A display methods area 1810 shows that the availabledisplay methods are a list, a tree, and a multi-select tree. When adisplay method is selected, a finish button 1820 is clicked to continue.

Finally, a confirmation interface 1900 is provided for the filter asshown in FIG. 19 that confirms that the filter has been createdsuccessfully using the wizard.

FIG. 20 shows the dashboard editor 400 with a member selection filter2020 (created as described above using the wizard) shown listed as anavailable filter. The filter workspace 1005 also shows no filterconnections in the linked item area 2030, since the member selectionfilter 2020 has not been linked yet. Once filters are created, thefilters can be linked to the scorecards and reports to which the filterswill be applied. To add the member selection filter 2020 to thedashboard, the user selects editor tab 450 to access the dashboardworkspace 430.

FIG. 21 shows the dashboard workspace 430 with a member selection filter2110 listed as an available filter. To add this filter to the dashboardworkspace 430, the member selection filter 2110 is dragged and droppedinto the top row zone 2120.

FIG. 22 shows the result of the drag and drop operation. (Note that thescorecard originally included in the top row zone has been removed forpurposes of clarity only. A zone can hold multiple objects, if desired.)In order for an item in the dashboard workspace 430, such as thescorecard in the bottom row of the workspace 430, to use the filter, thefilter must be connected to the item.

FIG. 23 shows an example screen for connecting the member selectionfilter 2310 to the analysis services basis scorecard 2320. The filter2310 can be dragged onto a drop area 2330 to connect the filter to thescorecard 2320.

When the filter is connected in the manner described, the user ispresented with the edit filter link dialog box 2400 as shown in FIG. 24.The link options tab 2410 is highlighted. This allows the user to selecta dashboard item endpoint which determines how the data will be used. Adrop down menu 2420 for the dashboard item endpoint provides choicesincluding filters, rows, columns, geography and time. In this example,filters is chosen for the endpoint. The user can also select a sourcevalue from dropdown menu 2430, and can enter a filter link formula byselecting a box 2440.

The user can also select a link items tab 2450 to show the default linkbetween the filter and the object that will be filtered. When configuredas described herein, these values are not editable. The user can alsoselect to define the connection between the filter and the object byusing the object drop down menu or the ribbon, as described furtherbelow.

Referring now to FIG. 26, the dashboard editor 400 is shown with thefilter applied. As shown, the scorecard in the bottom row zone of theworkspace 430 lists the filter (member selection) as part of thescorecard.

Referring now to FIG. 27, a zone in the workspace 430 can be edited byselecting the zone and using control elements on the ribbon 410, or byright-clicking to access a menu 2710. The menu 2710 allows the user toadd, split or remove zones until the zones of the dashboard representthe dashboard layout the user wishes to create. The user can also selectzone settings in the menu 2710 to change the settings of the zone.

In addition to accessing menus, the user can simply drag and drop zoneswithin the workspace 430 to change the placement of the zones. Forexample, the user can drag the zone located in the bottom row above thetop row to change the order of the zones.

Referring now to FIGS. 28-30, a zone settings interface 2810 is shown.The zone settings interface includes tabs 2820 that are used to accessgeneral, size, and orientation settings. With the general tab selectedin FIG. 28, the user can access a textbox 2830 to name the zone. Withthe size tab selected in FIG. 29, the user can access width setting area2910 and height setting area 2920 to set the width and height byauto-sizing or specifying a particular percentage of the page or pixelsize. With the orientation tab selected, the user can select orientationsettings 3010 including horizontal, vertical, and stacked.

Referring now to FIG. 31, any objects positioned in a zone, such asscorecards, will automatically expand when the cursor hovers over theobject to expose all of the options associated with the object. Forexample, when the cursor hovers over the fixed values scorecard in thetop row zone of the workspace 430, the zone automatically expands toprovide a list 3110 showing all of the options associated with thescorecard. This allows the size of the logical view for a particularzone to remain fixed while still allowing the user to access theinformation in smaller screen sizes.

Referring now to FIG. 32, an example dashboard 3200 is shown. Thedashboard 3200 has been created using the dashboard editor 400. Thedashboard 3200 can be published to a server (e.g., server 102 describeabove) so that the dashboard 3200 is accessible by a plurality ofclients (e.g., client 106) using, for example, a web browser 3205. Thedashboard 3200 includes metrics 3210, as well as a selection dropdown3220 that allows the user to sort the data shown on the dashboard 3200by quarter. Also, the dashboard 3200 includes a toolbar 3230 that allowsthe user to modify the format of the metrics 3210. For example, the usercan select control elements on the toolbar 3230 to change the sortdirections of the data or modify the filtering of the data. Otherconfigurations are possible.

Referring now to FIG. 33, an example method 3300 for creating adashboard is shown. Initially, at operation 3310, a template from thedashboard is selected having one or more zones. Next, at operation 3312,the dashboard is given a name. Control is then passed to operation 3314,at which a scorecard or report is dragged onto a zone of the dashboard.

At operation 3316, a determination is made as to whether or not a zoneneeds to be changed. If so, control is passed to operation 3318, and thezone can be changed (e.g., split, deleted, new zone added, etc.). if azone does not need to be changed, control is instead passed fromoperation 3316 to operation 3320.

At operation 3320, a determination is made as to whether or not a zoneneeds to be adjusted. If so, control is passed to operations 3322 and3324, at which the position and/or size of the zone can be adjusted. Ifa zone does not need to be adjusted, control is instead passed fromoperation 3320 to operation 3326.

At operation 3326, a determination is made as to whether or not a filteris needed. If not, control is passed to operation 3336, at which adetermination is made as to whether or not addition items need to beadded to the dashboard. If so, control is passed back to operation 3314.If not, control is passed to operation 3338, at which the dashboard canbe published to a server.

Referring back to operation 3326, if the determination is made that afilter is needed, control is instead passed to operation 3328. Atoperation 3328, a determination is made as to whether or not the desiredfilter exists. If the filter does not exist, control is passed tooperation 3330, at which the filter is created (see method 3400described below). If the filter does exist, control is instead passedfrom operation 3328 to operation 3332.

At operation 3332, the filter is dragged onto a zone of the dashboard.Next, at operation 3334, the filter is linked to a scorecard or reportin the dashboard. Next, control is then passed to operation 3336, asdescribed above.

Referring now to FIG. 34, an example method 3400 for creating a filterfor a dashboard is shown. Initially, at operation 3410, a template isselected for the filter. Next, at operation 3412, the filter is given aname. At operation 3414, the data source for the filter is selected.

Next, at operation 3416, the dimensions for the filter are selected. Atoperation 3420, the members for the filter are selected. Finally, atoperation 3422, the display method for the filter is selected.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

1. A method for creating a filter that is programmed to modify one or more scorecards or reports in a digital dashboard, the method comprising: allowing for selection of a filter template from a plurality of filter templates, the filter template defining a type of the filter; allowing for selection of a data source for the filter; allowing for selection of filter parameters from the data source; allowing for selection of a display method for the filter; and compiling, by a computing device, the filter from the filter template, the filter parameters, and the display method.
 2. The method of claim 1, further comprising: applying the filter to an element of the digital dashboard; and displaying the element with one or more filtered values.
 3. The method of claim 2, further comprising adding dimensions and members to the filter.
 4. The method of claim 3, further comprising selecting a method for displaying the element from a group consisting of a list, a tree, and a multi-select tree.
 5. The method of claim 1, further comprising adding dimensions and members to the filter.
 6. The method of claim 5, further comprising allowing a user to select a selected member of the members to access properties associated with the selected member.
 7. The method of claim 6, further comprising allowing the user to define a default member.
 8. The method of claim 1, further comprising selecting a method for displaying an element from a group consisting of a list, a tree, and a multi-select tree.
 9. The method of claim 1, further comprising providing a filter wizard to allow for creation of the filter.
 10. The method of claim 9, further comprising allowing the filter wizard to guide a user through creation of the filter.
 11. The method of claim 10, further comprising listing each step of creation of the filter in the filter wizard.
 12. The method of claim 1, further comprising allowing a user to name the filter.
 13. The method of claim 1, further comprising listing the filter in a dashboard, the filter being listed as one of a plurality of available filters for user selection.
 14. A method for creating a filter that is programmed to modify one or more scorecards or reports in a digital dashboard, the method comprising: providing a filter wizard to guide a user through creation of the filter, the filter wizard including: allowing for selection of a filter template from a plurality of filter templates, the filter template defining a type of the filter; allowing for selection of a data source for the filter; allowing for selection of filter parameters from the data source; allowing for selection of a display method for the filter; and compiling, by a computing device, the filter from the filter template, the filter parameters, and the display method; applying the filter to an element of the digital dashboard; and displaying the element with one or more filtered values.
 15. The method of claim 14, further comprising selecting a method for displaying the element from a group consisting of a list, a tree, and a multi-select tree.
 16. The method of claim 14, further comprising adding dimensions and members to the filter.
 17. The method of claim 16, further comprising allowing the user to define a default member.
 18. The method of claim 14, further comprising selecting a method for displaying the element from a group consisting of a list, a tree, and a multi-select tree.
 19. The method of claim 10, further comprising listing each step of creation of the filter in the filter wizard.
 20. A method for creating a filter that is programmed to modify one or more scorecards or reports in a digital dashboard, the method comprising: providing a filter wizard to guide a user through creation of the filter, the filter wizard listing each step of creation of the filter in the filter wizard, the filter wizard including: allowing the user to name the filter; allowing for selection of a filter template from a plurality of filter templates, the filter template defining a type of the filter; allowing for selection of a data source for the filter; allowing for selection of filter parameters from the data source; allowing for selection of a display method for the filter; adding dimensions and members to the filter; and compiling, by a computing device, the filter from the filter template, the filter parameters, and the display method; listing the filter in a dashboard, the filter being listed as one of a plurality of available filters for user selection; applying the filter to an element of the digital dashboard; and displaying the element with one or more filtered values. 